Pokémon We Caught

What wins and achievements did we capture this time?

We finally caught that legendary payment integration bug that's been evading us for weeks!
Shipped the new onboarding flow ahead of schedule — a shiny catch for sure.
Our pair-programming sessions levelled up the whole team's confidence.
Gym Battles We Fought

What challenges or obstacles did we battle along the way?

The deployment process knocked us out a few times before we figured out the fix.
Unclear requirements meant we kept rebattling the same scope discussions.
Too many context switches drained our HP across the week.
Badges We Earned

What new skills, lessons or insights did we gain?

Earned the 'Documentation Badge' by finally writing up our deployment runbook.
Learned that breaking stories down smaller made estimation way more accurate.
We discovered a faster way to run our test suite — knowledge worth keeping.
The Next Route

Where do we go next and what actions will get us there?

Let's automate the deployment steps before the next sprint begins.
Set up a shared requirements review to avoid rebattling scope.
Plan to invest one day into fixing the flaky tests.

What is the Pokémon Trainer's Journey retrospective

Gotta retro 'em all! The Pokémon Trainer's Journey retrospective transforms your team reflection into an adventure inspired by the world of Pokémon. Just as a trainer sets out from their hometown with big dreams, your team embarks on each sprint or project ready to catch wins, battle tough challenges, and level up along the way. This playful, themed format keeps energy high while still surfacing the honest insights every team needs to grow. Structured around four memorable stages of a trainer's journey, this retrospective invites participants to celebrate the Pokémon they caught (their achievements), reflect on the gym battles they fought (the challenges they faced), identify the badges they earned (skills and learnings gained), and chart the next route on their map (actions and goals for the future). The familiar gaming metaphors lower the barrier for sharing, encourage creative thinking, and make even difficult conversations feel approachable and fun. Ideal for agile teams, gaming communities, and anyone who loves a bit of nostalgia, this retrospective is a great way to break routine and keep your retros fresh. By framing progress as a continuous journey, teams build a growth mindset, recognise each other's contributions, and stay motivated to become the very best — like no team ever was. Whether you're wrapping up a sprint or a major release, this engaging format helps everyone reflect, connect, and plan their next adventure.

Pokémon Trainer's Journey retrospective format

Pokémon We Caught

What wins and achievements did we capture this time?

This is the celebration stage of the journey. Encourage participants to think of every 'Pokémon' they caught — from small bug fixes to major feature releases. Prompt the team to recognise both individual and collective wins, and make space for shout-outs so everyone feels their contributions were spotted. Keep the tone upbeat to set a positive momentum for the rest of the retro.

Gym Battles We Fought

What challenges or obstacles did we battle along the way?

Frame challenges as gym battles — tough but conquerable encounters that test the team. Invite honest reflection on what made things difficult, whether it was unclear requirements, technical debt, or competing priorities. Keep the focus constructive rather than blaming, and look for patterns that show up as recurring 'gym leaders' the team keeps facing.

Badges We Earned

What new skills, lessons or insights did we gain?

Badges represent the learnings and growth the team earned through the journey. Encourage participants to reflect on new skills, improved processes, or 'aha' moments — even ones that came from setbacks. This stage reinforces a growth mindset and helps the team appreciate how far they've travelled.

The Next Route

Where do we go next and what actions will get us there?

This is where the team plots the next leg of the journey. Turn the insights from earlier stages into concrete, ownable actions and goals. Encourage participants to be specific about who will do what, and keep the number of commitments realistic so the team can actually reach the next town.

When to use this retrospective

  • When your team needs a fun, themed break from standard retrospective formats to re-energise reflection.
  • At the end of a sprint, project milestone, or major release to celebrate progress and plan ahead.
  • For gaming communities, hackathon teams, or playful cultures that enjoy gamified facilitation.
  • When you want to encourage a growth mindset by framing learning and challenges as part of an ongoing journey.
  • To make difficult conversations feel safer and more approachable through familiar, lighthearted metaphors.

Suggested icebreaker questions

  • If you could have one Pokémon on your team this sprint, which would it be and why?
  • What's your team 'starter Pokémon' — the strength you always rely on to get going?

Ideas and tips for your retrospective meeting

  • Set the scene at the start by reminding everyone they are trainers on a shared adventure — it primes creative, playful contributions.
  • Timebox each stage so the celebration of wins doesn't crowd out time for actions and goals.
  • Make sure the 'Gym Battles' stage stays constructive and blame-free; focus on the obstacle, not the person.
  • Encourage shout-outs in the 'Pokémon We Caught' stage so quieter team members get recognised.
  • Limit the number of actions in 'The Next Route' to a few achievable commitments with clear owners.
  • Don't worry if not everyone knows Pokémon — keep the metaphors light and explain the meaning of each stage clearly.

Frequently asked questions

What is a Pokémon Trainer's Journey retrospective?
It's a themed, gamified retrospective that frames your team's reflection as a trainer's adventure — catching wins, fighting gym battles (challenges), earning badges (learnings), and planning the next route (actions). It keeps engagement high while still surfacing meaningful insights.
How long does a Pokémon Trainer's Journey retrospective take?
Most teams complete it in 45 to 60 minutes. Allow time for an icebreaker, brainstorming across the four stages, grouping and discussion, and agreeing on actions.
When should I use this retrospective format?
It works best at the end of a sprint, milestone, or release, and is especially good when you want a fun change of pace or need to make tough conversations feel more approachable.
Do my team members need to know Pokémon to take part?
No. The metaphors are intuitive and easy to explain — wins, challenges, learnings, and next steps — so anyone can participate fully even without knowing the games.
How is this different from a standard sprint retrospective?
It covers the same core ground as a typical retro but uses playful gaming themes to boost energy, encourage creativity, and frame progress as an ongoing journey that supports a growth mindset.
How do I run this retrospective in TeamRetro?
Select the Pokémon Trainer's Journey template, invite your team, and work through each of the four stages by brainstorming, grouping ideas, voting on what matters most, and capturing action items — all within TeamRetro.

New to retrospectives? Read our guide on how to run a retrospective →